docs(planner): document lifecycle-aware planning and costs - #320
Closed
zzylol wants to merge 34 commits into
Closed
Conversation
zzylol
force-pushed
the
test/workload-lifecycle-e2e
branch
from
August 30, 2026 18:21
2f4eb69 to
ec4ce8f
Compare
zzylol
force-pushed
the
docs/lifecycle-aware-planner
branch
from
August 30, 2026 18:21
5548824 to
15c2f5b
Compare
zzylol
force-pushed
the
test/workload-lifecycle-e2e
branch
from
August 30, 2026 18:30
ec4ce8f to
1056383
Compare
zzylol
force-pushed
the
docs/lifecycle-aware-planner
branch
from
August 30, 2026 18:30
15c2f5b to
0b81280
Compare
zzylol
force-pushed
the
test/workload-lifecycle-e2e
branch
from
August 30, 2026 18:35
1056383 to
ed53588
Compare
zzylol
force-pushed
the
docs/lifecycle-aware-planner
branch
from
August 30, 2026 18:36
0b81280 to
e815908
Compare
zzylol
force-pushed
the
test/workload-lifecycle-e2e
branch
from
August 30, 2026 18:46
ed53588 to
3a660e9
Compare
zzylol
force-pushed
the
docs/lifecycle-aware-planner
branch
from
August 30, 2026 18:46
e815908 to
347839f
Compare
…ase boundaries (#171) Add phase-explicit post-ASAP nodes SummaryExpr::{ExactTransform, ExactPostProcess} carrying a non-exhaustive ExactOperator::Aggregate payload (never an intact QueryExpr subtree), plus an ExecutionAvailability {UpdateValue, SummaryState, ReadoutValue} derivation/validation (post_asap::phase) returning typed PhaseErrors at construction. construct_summary_agg now validates its edge, so a maintained summary over a query-time readout falls back conservatively instead of producing an unexecutable plan. Add ExactCompositionStrategy (registered in default_strategies) proposing Replacement::ExactComposition candidates that reference the child target rather than selecting a child; PlanSpace::global_selection commits the compatible parent/child pair using the issue's cost-units-per-second formulas (postprocess/pretransform vs raw-recompute baseline), counts shared child state once, and GlobalSelection::materialize links the committed decisions into one validated DAG with shared Rc identity. Cost hooks: CostModel::mixed_execution_capabilities and exact_composition_cost_inputs (unknowns stay None, never zero; missing statistics keep KeepPreAsap). DAG export gains explicit per-node stage, decision provenance, cost unit and child-decision links (additive). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
zzylol
force-pushed
the
test/workload-lifecycle-e2e
branch
from
August 30, 2026 19:03
3a660e9 to
a8fedf2
Compare
zzylol
force-pushed
the
docs/lifecycle-aware-planner
branch
from
August 30, 2026 19:03
347839f to
312ff5a
Compare
zzylol
force-pushed
the
test/workload-lifecycle-e2e
branch
2 times, most recently
from
August 30, 2026 21:27
bf0f818 to
4e93a30
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #319.
Why
Lifecycle semantics, costs, guarantees, and CSE interactions need an architectural contract.
Before this PR
No top-down document explained how workload evidence becomes a deployment or which integrations remain deferred.
After this PR
A designer can follow recurring demand through alternatives and cost formulas to a guarantee and explained rejection, including shared-summary costing.
What and how
Verification
Stack
Base: #319. Next: #313.